Network message transmissions reduction systems and methods

ABSTRACT

Systems and methods for reducing the amount of messages transmitted in large-scale distributed mesh networks are disclosed. Network components include transceivers and memory storing instructions which, when executed by a processing unit, reduce transmissions made by the transceiver within the network. The instructions executed by processing unit could (1) create an expiration parameter to limit the number of times a signal is retransmitted, (2) form groups of network components from which one or a few of the group network components are designated to respond on behalf of the group, (3) keep advertising transmissions dormant by default until called upon, (4) employ a time delay parameter for a time interval in which no transmission may be made, and (5) include message IDs in control signals that are transmitted.

BACKGROUND

In structures such as houses and high-rise buildings, there may be manycomponents such as switches and sensors through which target devicessuch as fixtures and appliances are powered to turn such target deviceson/off through adaptors communicatively coupled to the target devices.These components may be grouped together to form one or more networks.When transceivers and processors are employed in some of these networkcomponents, a communication network employing a short-rangecommunications protocol may be formed in which the target devices may beturned on/off via the adaptors. Other network components such asinitialization/control (I/C) device and/or bridge devices may beincluded in the communications network through which a user may remotelyoperate and/or control the operations of the network. Examples of suchcommunication networks were disclosed in the following publications:U.S. Pat. No. 9,781,245 entitled “Networking Systems, Protocols, andMethods for Controlling Target Devices” and issued to Miller on Oct. 3,2017; and U.S. Pat. No. 10,237,391 entitled “Networking Systems,Protocols, and Methods for Controlling Target Devices” and issued toMiller on Mar. 19, 2019, each of which is incorporated herein in itsentirety.

In mesh communications networks like those disclosed in Miller, eachnetwork component may be assigned a unique network address defined byparameters stored in memory for the network component. These parametersmay include a location ID identifying the network and a unique device IDfor identifying the network component. Where the network component is acontroller (e.g., a switch or sensor) for controlling one or morecontrolled devices, the controller may be assigned a target ID parameterthat defines those network components that the controller is programmedto control. For example, the controller may store a target device ID orgroup ID stored in memory to indicate the controller's role ofcontrolling either one controlled device or a group of controlleddevices, respectively.

Network components are typically manufactured in a state with no storednetwork ID. In order to join a network, the device advertises that it isavailable for connection and is added to a network via standard messagesthat can be read without requiring encryption keys. Upon selecting adevice to add to a specific network, the device is provided a securitykey, network ID, and other relevant parameters by the programmingdevice. Thereafter the device no longer advertises its availability forconnection and will only operate within the specific network. Thisapproach has the advantage of allowing any person with a programmingdevice to add the device to a network, but it also opens a securityvulnerability that may allow non-authorized users to add their ownsecurity ID and limits the functionality that can be applied to thedevice because many features are disabled prior to a device having avalid security key. These factors constrain the applicability ofprogramming and diagnostic tools, especially those operating remotely,because (for security reasons) most features of the target device aredisabled for remote access until a network ID is present.

Adaptors are network components configured to receive control signalsand implement those control signals on one or more communicativelycoupled target devices. A user can add an adaptor to the communicationsnetwork by programming these adaptors (e.g. using an I/C device) with alocation ID, a unique device ID, and/or a group ID. When an adaptorreceives a control signal containing a target ID that matches itslocation ID and the device ID or group ID, the adaptor can implement thecontrol signal on the target device(s) coupled thereto. Control signalsdestined for the device ID or group ID of the adaptor are received andimplemented on the communicatively coupled target device(s).

The scalability of a distributed communications network is dependent ona number of factors, including the size and volume of messages exchangedover the network. The number of messages exchanged over the network maydepend, in turn, on the number of times each message is relayed betweennodes, and the number of “background” or “overhead” messages used toconnect nodes and otherwise maintain the network. For example, when aroom is occupied, motion sensors in the room may generate large numbersof motion trigger events. If all motion trigger events are sent to everyother network component in the distributed communications network thenetwork can quickly become congested with unnecessary network traffic.Additionally, when operating a mesh communications network usingBLUETOOTH® devices, each radio constantly advertises, thereby generatingconsiderable background traffic that can limit the bandwidth availablefor necessary messages.

Additionally, it is often difficult to determine the status ofcontrolled devices in a mesh communications network because each devicemust be polled individually. When hundreds or thousands of nodes arepresent, this task can be very time consuming. The network trafficcreated by requesting the statutes of many nodes at once can render thenetwork unavailable for other tasks, such as turning on a light using amotion sensor or switch configured to communicate with the network.

These factors limit the scalability of the mesh communications networkbecause individual network nodes have limited processing speed andmemory for handling messages. Too many messages can overflow the nodes'memory buffers, potentially leading to control signals arriving at thedestination out of order or not being received at the destination atall. Thus, when networks of hundreds or thousands of nodes are deployedin a single area such as a building or home, desired messages may notpass quickly and successfully through the network.

SUMMARY

Embodiments of the inventive concepts disclosed herein are directed tosystems, protocols, and methods for reducing the amount of messagestransmitted in large-scale distributed mesh networks employingshort-range communications protocol(s). The systems and methods could beemployed individually or collectively to reduce the burden of excessivemessage transmissions. As a result, messages may be rapidly and reliablysent and received, influence caused by nearby radios employing protocolssuch as BLUETOOTH®, Wi-Fi®, and Zigbee® may be reduced, and impact tothese nearby radios employing such protocols may be limited.

Generally speaking, systems and methods are disclosed for improving thescalability of a distributed communications network by reducing thenumber of message transmissions required to successfully operate thedistributed communications network. For purposes of this disclosure,network components in a distributed communications network (alsoreferred to as “nodes”) may be conceptualized as “source nodes” thatgenerate particular control signals, “intermediate nodes” thatretransmit, or “forward,” received control signals, and “destinationnodes” that implement received control signals. In the event that adestination node is part of a group, the destination node may also actas an intermediate node, forwarding received control signals to ensurethat those signals reach each member of the group.

In some embodiments, systems and methods are provided for improving thescalability of a distributed communications network by utilizingmessages that include an expiration parameter. In these embodiments, anode receiving the message determines whether the message is eligiblefor retransmission. If the message is eligible for retransmission, thenode can adjust the expiration parameter within the control signal andforward the control signal with the adjusted expiration parameter.Designating an expiration parameter for a message sent over adistributed communications network can help strike a balance betweenallowing messages to be retransmitted through the network by other nodesenough times that the message reliably reaches its destination whilealso reducing unnecessary retransmissions to prevent overloading thenetwork's capacity.

In some embodiments, systems and methods are provided for improving thescalability of a distributed communications network by grouping togetherone or more network components to form a responder group of networkcomponents. A transceiver found in network component could include agroup responder parameter indicative of whether a particular network,the “group responder,” component will respond on behalf of the othergroup components. Thus, when a network component receives a messagerequesting a response from a group of network components, it willdetermine whether it has been designated as a group responder for thegroup and, if so, transmit the response message. Reducing the number ofnetwork components asked to respond to a status request can greatlyreduce the volume of network traffic that would otherwise be generated.

In some embodiments, systems and methods are provided for improving thescalability of a distributed communications network by reducingunnecessary network traffic in the form of advertising messages. Inthese embodiments, advertising messages may be turned off by default.When another network component, such as an Initialization/Control(“I/C”) device wishes to establish a direct connection to an adaptor orcontroller, it sends an “activate” command to nearby network components,asking those network components to begin advertising (e.g, for aspecified period of time). This technique permits connections betweennearby devices without requiring each network component in thedistributed communications network to advertise its presence at alltimes.

In some embodiments, systems and methods are provided for improving thescalability of a distributed communications network by preventing sourcenodes from initiating two instances of the same message within aspecified time period. For example, a motion sensor may be preventedfrom initiating two control signals for turning on a group of lightswithin a specified period of time. For example, lights controlled by amotion sensor are typically programmed to turn off after a specifiedperiod of time after not having received an indication from the motionsensor that the room remains occupied. The motion sensor may beprevented from sending new control signals until shortly before thelights are programmed to turn off.

In some embodiments, systems and methods are provided for improving thescalability of a distributed communications network by preventing anetwork component from forwarding a message that it forwarded oncebefore. In these embodiments, a source node may generate a message thatincludes a unique message ID parameter. When an intermediate ordestination node receives the message, it can determine whether themessage is eligible for retransmission by cross-referencing the messageID in the received message against the message IDs of message it hasalready received and forwarded. If the message ID is on the list ofalready forwarded messages, the node will not forward the message. Ifthe message ID is not on the list, however, the node can forward themessage and add the message ID parameter to the list of alreadyforwarded messages. This concept is distinguished from Time to Live(TTL) which increments a message count whether or not the specificdevice in question has seen the message before.

In some embodiments, network components may be shipped to the networklocation with a generic network ID and security key already stored inmemory, thereby unlocking increased functionality such as remote accessand encrypted communications, for example. The generic network ID may bekept confidential by the manufacturer and may be used to initiallyinstall and initialize a new mesh communications network by anauthorized user who has been given access to the generic network ID andsecurity key. Because the network components arrive at the installationsite already programmed with a generic network ID and/or security key,general advertising can be disabled, and access by unauthorized thirdparties who do not have access to the generic network ID and securitykey is restricted. Once the new mesh network is established, eachnetwork component may be re-programmed with a network-specific networkID and/or security key.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects and advantages of the invention will becomemore apparent upon consideration of the following detailed description,taken in conjunction with accompanying drawings, in which like referencecharacters refer to like parts throughout, and in which:

FIGS. 1A-1K illustrate an exemplary distributed communications networkthat may reduce the number of transmissions performed by networkcomponents configured with a transceiver for receiving and forwardingsignals, in accordance with some embodiments;

FIG. 2 is a flowchart of an exemplary method for reducing the number ofmessage transmissions in the distributed mesh network of FIGS. 1A-1G, inaccordance with some embodiments;

FIGS. 3A-3D illustrate another exemplary distributed communicationsnetwork that may reduce the number of transmissions performed by networkcomponents configured with a transceiver for receiving andretransmitting signals, in accordance with some embodiments;

FIG. 4 is a flowchart of an exemplary method for reducing the number ofmessage transmissions in the distributed mesh network of FIGS. 3A-3D, inaccordance with some embodiments;

FIGS. 5A-5K illustrate another exemplary distributed mesh network thatmay reduce the number of transmissions performed by network componentsconfigured with a transceiver for receiving and retransmitting signals,in accordance with some embodiments;

FIG. 6 is a flowchart of an exemplary method for reducing the number ofmethod transmissions in the distributed mesh network of FIGS. 5A-5K, inaccordance with some embodiments;

FIG. 7 is a flowchart of an exemplary method for reducing the number oftransmissions in a distributed mesh network, in accordance with someembodiments; and

FIG. 8 is a flowchart of an exemplary method for reducing the number ofmessage transmissions in a distributed mesh network, in accordance withsome embodiments.

DETAILED DESCRIPTION OF THE DISCLOSURE

In the following description, several specific details are presented toprovide a thorough understanding of embodiments of the inventiveconcepts disclosed herein. One skilled in the relevant art willrecognize, however, that embodiments of the inventive concepts disclosedherein can be practiced without one or more of the specific details, orin combination with other components, etc. In other instances,well-known implementations or operations are not shown or described indetail to avoid obscuring aspects of various embodiments of theinventive concepts disclosed herein.

Some advantages and benefits of the inventive concepts disclosed hereinare shown in FIGS. 1A through 8, illustrating how the communicationnetwork 100 may reduce the number of transmissions performed by networkcomponents, each of which is configured with a transceiver for receivingand forwarding messages via a short-range communications protocol untilsuch messages reach their intended destination(s). As used herein, theterm “message” refers to any message transmitted from one node toanother over the short-range communications protocol employed by thedistributed communications network. The term “control signal” refers toany message that includes a target ID and a control command for thedestination node(s) associated with the target ID to implement. The term“target ID” refers to a “device ID” or a “group ID.”

Referring now to FIG. 1A, communications network 100 is configured as abasic distributed mesh network suitable for implementation of theinventive concepts described herein. Communications network 100 includesa plurality of network components programmed with a common network ID,including source node 110, intermediate nodes 120, and destinationnode(s) 130. These nodes are peers in a distributed communicationsnetwork and communicate with one another via transceivers enabled forsending messages using short-range communications protocols.

Prior to installation and/or initialization, each network component maybe pre-programmed with a generic network ID. The generic network ID is avalue stored in the network component's memory (e.g. in a network IDfield) that does not represent any specific, established meshcommunications network. For example, the device manufacturer maypre-program each network component with a generic network ID beforeselling providing the network component to an installer or consumer.Knowledge of generic network ID is preferably retained by themanufacturer or otherwise made known only to those involved ininstalling and initializing a new mesh communications network, therebylimiting access to non-authorized users. Each network component may alsobe pre-programmed with a security key used for encrypted communicationsbetween network components.

Because each network component ships having been pre-programmed with ageneric network ID and/or security key, general advertising can bedisabled, improving security by minimizing access to non-authorizedusers who do not possess the generic network ID and/or the security key.Additionally, pre-programming network components in this waybeneficially safely permits increasing the range of commissioning anddiagnostic functionalities available to network components before theyare explicitly added to a network. Once a system has been installed andcommissioned, the general encryption key can be replaced by a buildingspecific key, thereby securing the network to a specific account andremoving the risk that a specific network could be accessed if thegeneric key is compromised. This is particularly effective because thetime from when a device is first installed in a location and when thesystem is fully commissioned and transitioned to a building specific keyis quite short, from less than a day to a few weeks at most. In someembodiments, the generic key can be changed periodically, limiting therisk that a compromised key could be used widely. Further, the networkkey update can be accomplished using the full encrypted security of thenetwork, allowing the key update to be performed remotely.

Once encrypted with a network-specific network ID and/or security key,network components are no longer accessible with the generic key, andthe security key can only be applied if the current building key isheld. Full power reset of the device (which can only be performedlocally via a button push, power cycle sequence, or other local means)will restore the device to a raw state with no security key, so thegeneral network key cannot be read from device memory once it has beenassigned a specific building key.

Source node 110 may represent any network component capable ofgenerating a control signal and transmitting that signal over thedistributed communications network. The control signal may be generatedin response to a user input (e.g., a user flipping a switch orinteracting with a user interface of an I/C device), an environmentalinput (e.g., physical motion captured by a motion sensor), apre-programmed command (e.g., a command for turning particular lights onor off at a scheduled time), or a command received at a remote accessbridge from a device located outside of the distributed communicationsnetwork. Thus, for example, source node 100 may represent aninitialization/control (“I/C”) device, remote access bridge (“bridge”),or any other controller, such as a switch or sensor. The designation ofa node as a source node simply means that that node was the noderesponsible for generating a particular message.

In some embodiments, systems and methods are provided for improving thescalability of a distributed communications network by utilizing abridge device asymmetrically such that inbound and outbound messages arehandled differently. For inbound messages received at a bridge devicefrom outside the distributed communications network, the bridge devicegenerates and transmits messages just like any other source node of thenetwork. The bridge device, being a peer node, can also act as anintermediate node, forwarding messages throughout the network asappropriate.

For outgoing messages destined for a location outside the distributedcommunications network, however, the bridge device may be configured toreceive and process many messages from a large number of networkcomponents at once. For example, the bridge device may be provided witha larger antenna than those used by other network components within thedistributed communications network such that it receives messages frommore distant network components than other nodes of the network. Thistechnique permits messages destined for a location outside of thedistributed communications network to be sent with a relativelyaggressive expiration parameter, thereby limiting the traffic requiredto send these messages out of the network.

In some embodiments, a bridge device for handling outgoing messages maybe the same bridge device that handling incoming messages. In otherembodiments, however, a distributed communications network can includemore than one bridge device, with the bridge device that handlesoutgoing messages being configured with a more powerful antenna andprocessor for receiving and processing messages than the bridge devicethat handles incoming messages. In a further embodiment, the two typesof bridges may be contained within a single form factor where eachbridge is assigned its own device ID when initialized.

In order for the outgoing bridge to process messages from a multiplicityof network nodes simultaneously (as opposed to handling messages one ata time) the outgoing bridge can employ post-collection data-processingtechniques in order to eliminate duplicate message, decrypt messages asnecessary, and then forward the message(s) out of the network (e.g., toa cloud server or other remote data collection system).

Destination node(s) 130 may represent any network component(s) capableof receiving a control signal over the distributed communicationsnetwork and implementing that signal. Thus, for example, destinationnode 130 may represent an adaptor that is coupled to a target device.The designation of a node as a destination node simply means that thatnode was the target of a particular control signal.

Intermediate nodes 120 may represent any network components that receivea message over the distributed communications network and forward themessage without implementing a control signal. Because all networkcomponents in the distributed communications network are peers, allnodes other than source node 110 and destination node(s) 130 arepotential intermediate nodes.

Referring now to FIG. 1B, assume that source node 110 has transmitted acontrol signal 112 (divided into signals 112 a through 112 i toillustrate that the same signal may be received by more than one othernode) to other nodes of the communication network 100 at time t(0). Thecontrol signal may include a location ID (identifying the network), atarget ID for the destination node(s), and a command to be performed bythe destination node upon being received.

Control signal 112 may include an expiration parameter (e.g., atime-to-live (“TTL”) parameter) that limits the number of times thecontrol signal may be forwarded before being allowed to expire. For thepurpose of illustration and not of limitation, the TTL at the sourcenode 110 is assumed to have a measurement value equal to 200. In someembodiments, a unit of the measurement could be expressed as number ofretransmissions as shown in this example. In some embodiments, a unit ofthe measurement could be expressed in time.

A suitable TTL value for a particular message may depend on a number offactors, including the number of network components in communicationsnetwork 100 and whether control signal 112 is being issued from astationary source node, such as a switch or motion sensor, or a roamingsource node, such as mobile phone acting as an I/C device. For example,in a large distributed communications network containing thousands ofnetwork components, a relatively large TTL parameter may be required toensure that the control signal reaches the destination nodes.Additionally, if control signal 112 is transmitted from a stationarysource node, it may be appropriate to set the TTL parameter to arelatively small number (e.g., 5) on the assumption that the stationarysource node will only be responsible for controlling devices in theimmediate vicinity. The TTL value is preferably set at the time thenetwork component is initialized. However, in some embodiments a userinitiating a control signal may choose a particular TTL value at thetime the message is sent. Further a user utilizing an I/C device mayalter the TTL value for messages originating from any network componentin communications network 100 at any time (e.g., when network componentsare added or removed from communications network 100, when it isdetermined that messages originating from a particular source node donot reliability reach one or more destination nodes, or when it isdetermined that messages originating from a particular source node canreliably reach the destination node(s) with a more aggressive TTLvalue).

Referring now to FIGS. 1C and 1D, assume that the intermediate nodes 120a and 120 b receive signals 112 a and 112 b at time t(1), determine thattheir device IDs and group IDs do not match the target ID specified inthe control signal, and retransmit each as signals 112 c and 112 d attime t(2) as shown. Intermediate nodes 120 a and 120 b each decrementthe TTL parameter by one to 199 before the retransmission. It should benoted that, although this example the use of the TTL parameter as adecreasing parameter, the embodiments discussed herein are not limitedto such operation of the TTL parameter; rather, in some embodiments, anoperation performed on the TTL parameter could include any operationwhich enables a monitoring of retransmissions of the control signal 112before expiring.

Referring now to FIGS. 1E and 1F, assume that intermediate nodes 120 cand 120 d receive signals 112 c and 112 d at time t(3), determine thattheir device IDs and group IDs do not match the target ID specified inthe control signal, and retransmit each as signals 112 e and 112 f att(4) as shown. As observed, intermediate nodes 120 c and 120 d eachdecrement the TTL parameter by one to 198 before retransmission.

Referring now to FIGS. 1G and 111, assume that intermediate nodes 120 eand 120 c receive signals 112 e and 112 f at time t(5), determine thattheir device IDs and group IDs do not match the target ID specified inthe control signal, and retransmit each as signals 112 g and 112 h attime (6) as shown. As observed, the intermediate nodes 120 e and 120 ceach decrement the TTL parameter by one to 197 before retransmission.

Referring now to FIGS. 1I and 1J, assume that destination node 130 andintermediate node 120 e receive signals 112 g and 112 h at time t(7) asshown, and intermediate node 120 e retransmits each as signal 112 i attime t(8) as shown. As observed, intermediate node 120 e determines thatits device ID and group ID do not match the target ID specified in thecontrol signal, and decrements the TTL parameter by one to 196 beforethe retransmission.

Because signal 112 g has reached the destination node 130, destinationnode 130 could be instructed not to retransmit this signal. For example,if control signal 112 g specified destination node 130's device ID inthe target ID field, destination node 130 can determine that no othernetwork component in communications network 100 needs to receive thesignal and determine that further retransmission would be unnecessary.However, if control signal 112 g specified destination node 130's groupID, destination node 130 may determine that there could be other networkcomponents in communications network 100 still waiting to receive thesignal. In that case, destination node 130 can implement the controlcommand and then decrement the TTL parameter and retransmit the messagejust like any other intermediate node.

Referring now to FIG. 1K, assume that the destination node 130 receivescontrol signal 112 i at time t(9). Upon receiving signal 112 i,destination node 130 could be instructed to not retransmit this signal.For example, as described below with respect to FIG. 8, destination node130 may determine that it has already received and retransmitted and/orimplemented control signal 112 i and that it should not attempt tore-implement the command contained within the signal or retransmit thecontrol signal to other network components within communications network100.

Referring now to FIG. 2, flowchart illustrating an exemplary method 200for reducing the number of transmissions performed by the networkcomponents of the communications network 100. Each network component mayinclude a processor programmed or otherwise configured to executeinstructions to perform the method of method 200. For each networkcomponent, the instructions may be stored in memory communicating withthe processor and can include code that determines whether to send,implement, and/or forward a control signal based on the networkcomponent's location ID and device ID or group ID, as well as the valueof an expiration parameter (e.g., a TTL value located in the controlsignal).

An initial value for the TTL parameter, or other expiration parameter,may be set depending on a number of different factors with the goalbeing to reduce the number of messages required to ensure successfuldelivery of the message to the destination node(s). One factor used todetermine a suitable TTL value for a particular message may be the totalnumber of network components in the distributed communications network.For example, the in a distributed communications network having morethan one-thousand network components, the TTL parameter might be set toa range of 100 to 200 to ensure successful operation. Another factoraffecting the necessary TTL value for successful operation is thephysical density of network components in the network. Where the networkcomponents are confined to a relatively small physical area, the TTLparameter may be set to relatively aggressive value in view of the factthat each message transmission will reach a relatively large number ofnetwork components. On the other hand, as the physical footprint of thedistributed communications network increases, the TTL parameter may needto be set to a higher value to ensure successful operation. In someembodiments, each potential source node may be programmed to generatemessages having a unique TTL value that suitably matches the node's rolein the distributed communications network.

For example, an immobile switch that is configured only to controltarget devices within a limited physical space (e.g., a single room) maybe configured to generate messages having a very aggressive TTL value(e.g., a value in the range between 1 and 5) whereas an VC device thatcan move throughout the network, and other “master controllers” that arecapable of controlling each device within the network, might beconfigured to generate messages having a higher TTL value (e.g., a valuein the range between 10 and 20).

At step 202, one or more network components of communications network100 receives a control signal transmitted from a source node thatoriginated the control signal. In these embodiments, control signalinclude an expiration parameter, such as a TTL parameter, along with thelocation ID and device or group ID of the one or more destination nodesto which the control signal is addressed. In some embodiments, thecontrol signal can also include a message ID that uniquely identifiesthe message.

At step 204, in response to receiving the control signal, each networkcomponent determines whether the control signal is eligible forretransmission. For example, each network component can determinewhether the message has expired by comparing the expiration parameter toan expiration threshold. In the case that the expiration parameter is aTTL parameter, each network component receiving the message will forwardthe message so long as the TTL value is not set to 0. In someembodiments, each network component receiving the message alsodetermines whether or not it already forwarded the message, (e.g., bycross-referencing the control signal's message ID against message IDsfor recently forwarded messages) the node can refrain from forwardingthe message again.

If the control signal is received at a destination node (i.e. a networkcomponent that matches either the device ID or group ID specified in thecontrol signal), the destination node may or may not forward the controlsignal. For example, if the message specifies the node's device ID, thedestination node may determine that it should not forward the message.However, if the message specifies a group ID, the destination node maydetermine that it should forward the message to ensure that the othernodes associated with the group ID receive the message.

At step 206, each network component that receives the control signaldetermines whether the TTL parameter has reached its expiration limitand, based on the determination, determines whether or not to forwardthe message. If a network component determines that it should forward areceived message, it can adjust the TTL parameter accordingly and, atstep 208, forward the message.

Referring now to FIG. 3A, a communication network 300 configured as asecond basic distributed mesh network suitable for implementation of theinventive concepts described herein is presented. Communications network300 includes a plurality of network components represented as aplurality of nodes 310 through 330, inclusive, in short-rangecommunications with other nodes via the transceivers of the networkcomponents. Source node 310 could include any network componentprogrammed with instructions for requesting the status of networkcomponents. Group 320 could be comprised of a plurality of group nodes320 a through 320 c representative of a plurality of network componentssuch as a plurality of controllers and/or a plurality of adaptors.Destination node 330 that could also be representative of a controllerand/or an adaptor through which one or more controlled devices may becontrolled. In some embodiments, although each of the network componentsin group 320 are assigned a unique device ID, each may share the samelocation ID and group ID.

In some embodiments, network components may be assigned a separateresponse group ID that identifies a group of network componentsindependently from the “group ID” used to define a group of networkcomponents for the purposes of receiving and implementing controlsignals. For example, a response group ID may be assigned to a group ofnetwork components in close proximity to one another (as opposed to thegroup ID, which is used to control group behavior regardless of thenetwork component's location within the network.

In some embodiments, response group IDs may be generated and updateddynamically. For example, each network component may dynamicallydetermine those network components within one hop via the short-rangecommunications protocol to create a network map. The network map maythen be segmented into a number of response groups. Each response groupmay be assigned a single group responder. Preferably, the groupresponder is located one hop from each other network component in theresponder group to reduce the number of messages required for each groupresponder to poll the network components in its response group.

In some embodiments, source node 310 initiates a general status requestthat does not identify any particular device ID or group ID. Then when anetwork component receives a status request, it can forward its statusto its group responder, which then forwards information regarding thestatus of each node in its responder group. If the group responder doesnot receive a status update from one or more device in its responsegroup within a predetermined period of time after receiving a firststatus update message, it may independently poll the network componentsin its responder group to determine the node's status.

In some embodiments, source node 310 initiates a status requestspecifically addressing each group responder. The set of all groupresponders in a communications network may be assigned a particulargroup ID, which the source node uses to poll those group responders.This group ID may be set, for example, upon initiation of a networkmapping function. In various embodiments, the network mapping functionmay be initiated by a user (e.g. a person operating an PC device, on apre-determined schedule. In some embodiments, the network mappingfunction may be initiated when a change to the network topology isdetected. For example, if a group responder does not receive a responseto a status check, it will not return a response for that node, and itmay be determined that there has been a change to the network topology,initiating a new network mapping function. In some embodiments, thegroup responder's status check message may be set with a TTL of 1, sothat it only responds with the status of those nodes within one hop.

In keeping within the spirit of the invention, the network may may bestored in a decentralized manner, with no single node storing the entirenetwork map. In principle, each network component stores only one ormore group responder IDs that indicate which of the one or moreresponder groups the node belongs to and a parameter that indicateswhether the particular network component is a group responder for itsresponder group.

Referring now to FIG. 3B, assume that the source node 310 hastransmitted a control signal 312 (divided into signals 312 a through 312c) to other nodes of the communication network 300 at time t(0). Thecontrol signal may include the location ID and the group ID of the group320 represented by group nodes 320 a through 320 c, and a request forstatus of the group nodes 320 a through 320 c.

Referring now to FIG. 3C, assume that the group nodes 320 a through 320c receive signals 312 a through 312 c at time t(1) as shown.

Referring now to FIG. 3D, group node 320 a has retransmitted signal 312a as signal 312 d at time t(2) but has not responded to the request.Also, for the sake of discussion, assume that group nodes 320 c has beenassigned or designated to be a group responder for the group 320. Asillustrated, group responder node 320 c has transmitted a signal 314responding to the request at time t(2) while the others group nodes ofthe group 320 do not. In some embodiments, although only group node 320c has been assigned the role of group responder, more than one groupnode may be assigned the role.

Referring now to FIG. 4, flowchart 400 is depicted disclosing an exampleof a second method for reducing the number of transmissions performed bythe network components of the communication network 300, where eachnetwork component may include a processing unit programmed or configuredto execute instructions to perform the method of the flowchart 400. Foreach network component, the instructions may be stored in memorycommunicating with the processing unit and include location ID, groupID, and designated responder ID parameters of the network component,where the latter parameter could an indicator (e.g., a flag that is set)used to indicate a network component that responds on behalf of a groupof which it is part, where the number of such responding groupcomponents is less than the total number in the group. In someembodiments, there could be only one responding group component. In someembodiments, fewer than half of the group components could be respondinggroup components.

The method of flowchart 400 begins with module 402 with one or morenetwork components of the communication network 300 receiving a controlsignal transmitted from a source network component(s) from which thecontrol signal originates. In some embodiments, the control signal couldinclude location ID and group ID parameters of a defined group ofnetwork components to which the control signal is directed. In someembodiments, the control signal could include a request for informationor feedback from the group of network components to which assigned groupresponder(s) may respond. In some embodiments, a destination groupdiscussed herein could be a group of controller(s) and/or an adaptor(s)assigned or sharing the same location ID and group ID parameters.

The method of flowchart 400 continues with module 404 with each networkcomponent, in response to receiving the control signal, determiningwhether it is a destination group component that is part of thedestination group from at least the location ID and group ID parameters.

The method of flowchart 400 continues with module 406 with anintermediate network component (i.e., a network component that is not adestination group component having the group ID parameter) mayretransmit the control signal if the determination is negative, that is,the network component is not part of the destination group.

The method of flowchart 400 continues with module 408 with eachdestination group component, upon a positive determination, determiningfrom its designated responder ID parameter whether it has been assignedthe role of group responder or not.

The method of flowchart 400 continues with module 410 with eachdestination group component, upon determining that it has been assignedthe role of group responder, transmitting a control signal on behalf ofthe group in response to the operation requested in the received controlsignal. Then, the method of flowchart 400 ends.

Referring now to FIG. 5A, a communication network 500 configured as athird basic distributed mesh network suitable for implementation of theinventive concepts described herein is presented.

Communication network 500 includes a plurality of network componentsrepresented as a plurality of nodes 510 through 530, inclusive, inshort-range communications with other nodes via the transceivers of thenetwork components. A source node 510 could be any network componentprogrammed with instructions for requesting network components toactivate a transmission channel advertising its presence to othernetwork components. A plurality of intermediate nodes 520 a through 520e, inclusive, could be representative of a plurality of controllersand/or a plurality of adaptors; and a destination node 530 that couldalso be representative of a controller and/or an adaptor through whichone or more controlled devices may be controlled. In some embodiments,the second channel could be one employed by Bluetooth communicationprotocols. In some embodiments, the control signal could include a TTLparameter having a relatively small measurement value (e.g., TTL=10) tolimit the number of retransmissions to limit the area in which therequest to wake up is transmitted.

Referring now to FIG. 5B, assume that the source node 510 hastransmitted a control signal 512 to other nodes of the communicationnetwork 500 at time t(0). In addition to a TTL parameter, the controlsignal may include an enable request parameter to request each networkcomponent receiving within the communications short-range to enable oractivate their respective transmit mode by switching from itstransmit-off (or receive-only) mode. In some embodiments, this modecould be the default mode.

Referring now to FIGS. 5C and 5D, assume that the intermediate nodes 520a and 520 b receive signals 512 a and 512 b at time t(1) and retransmiteach as signals 512 c and 512 d at time t(2) as shown. As observed, theintermediate nodes 520 a and 520 b have been instructed by the enablerequest parameter to enable (i.e., turn on) their respective transmitmodes so that they may repeatedly transmit their availability to theother nodes within the communications short-range the as well asdecrement the TTL parameter by one to 9 before the retransmission.

Referring now to FIGS. 5E and 5F, assume that the intermediate nodes 520c and 520 d receive signals 512 c and 512 d at time t(3) and retransmiteach as signals 512 e and 512 f at t(4) as shown. As observed, theintermediate nodes 520 c and 520 d have been instructed by the enablerequest parameter to enable their respective transmit modes so that theymay repeatedly transmit their availability to the other nodes within thecommunications short-range the as well as decrement the TTL parameter byone to 8 before the retransmission.

Referring now to FIGS. 5G and 5H, assume that the intermediate nodes 520e and 520 c receive signals 512 e and 512 f at time t(5) and retransmiteach as signals 512 g and 512 h at time (6) as shown. As observed, theintermediate nodes 520 e and 520 c have been instructed by the enablerequest parameter to enable their respective transmit modes so that theymay repeatedly transmit their availability to the other nodes within thecommunications short-range the as well as decrement the TTL parameter byone to 7 before the retransmission.

Referring now to FIGS. 51 and 5J, assume that the destination node 530(as may be provided by location ID and device ID parameters in signal512) and intermediate node 520 e receive signals 512 g and 512 h at timet(7) as shown, and intermediate node 520 e retransmits it as signal 512i at time t(8) as shown. As observed, the intermediate node 520 e hasbeen instructed by the enable request parameter to enable its respectivetransmit mode so that it may repeatedly transmit its availability to theother nodes within the communications short-range the as well asdecrement the TTL parameter by one to 6 before the retransmission.Because signal 512 g has reached the destination node 530, thedestination node 530 could be instructed to ignore the enable requestparameter.

Referring now to FIG. 5K, assume that the destination node 530 receivessignal 512 i at time t(9). As discussed in the preceding paragraph, thedestination node 530 could be instructed to ignore the enable requestparameter.

Referring now to FIG. 6, flowchart 600 is depicted disclosing an exampleof a third method for reducing the number of transmissions performed bythe network components of the communication network 500, where eachnetwork component may include a processing unit programmed or configuredwith execution instructions to perform the method of the flowchart 600.For each network component, the instructions may be stored in memorycommunicating with the processing unit and include an enable/disablemode parameter indicating whether or not the transmit mode of thetransceiver is enabled along with a response of enabling or turning onits transmit mode upon receiving an enable request parameter.

When switched to the enable mode, the network component may be enabledto advertise its presence to the other network components for a limitedtime that may be defined by a user.

The method of flowchart 600 begins with module 602 with one or morenetwork components of the communication network 500 receiving a controlsignal transmitted, via short-range communications protocol, from asource network component(s) from which the control signal originates. Insome embodiments, the control signal could include an enable requestparameter along with a TTL parameter.

The method of flowchart 600 continues with module 604 with each networkcomponent, in response to receiving the control signal, enabling itstransmit mode if not enabled. In some embodiments, the network componentcould enable its transmit mode for a limited time interval as defined bya user. In some embodiments, an intermediate network component mayadjust the TTL parameter to reduce the number of retransmissionsremaining if the TTL parameter has not reached its expiration limit.

The method of flowchart 600 continues with module 606 with eachintermediate network component repeatedly transmitting its availabilityto the other network components within the commutations short-range fora limited time as defined by the user.

The method of flowchart 600 continues with module 608 with each networkcomponent, in response to receiving the control signal, determiningwhether the control signal is eligible for retransmission, where suchdetermination could be performed in a similar manner as discussed inmodule 204 above.

The method of flowchart 600 continues with module 610 with eachintermediate network component being eligible (i.e., not the destinationnetwork component) receiving the control signal adjusting the TTLparameter, where such adjustment could be performed in a similar manneras discussed in module 206 above.

The method of flowchart 600 continues with module 612 with eachintermediate network component, if eligible, transmitting the controlsignal with the adjusted TTL parameter, where such transmission could beperformed in a similar manner as discussed in module 208 above. Then,the method of flowchart 600 ends.

Referring now to FIG. 7, flowchart 700 is depicted disclosing an exampleof a fourth method employing delay modes for reducing the number oftransmissions performed by the network components of the communicationnetworks discussed herein, where each network component may include aprocessing unit programmed or configured with execution instructions toperform the method of the flowchart 700. In some embodiments, thecontroller could be a source network component configured as a motionsensor. For each network component, the instructions may be stored inmemory communicating with the processing unit and include network ID anddevice ID parameters of the network component. In some embodiments, theinstructions could include control of a delay mode parameter of thecontroller indicating whether or not a delay mode is enabled; whenenabled, the subsequent transmission of instructions from the controllerto its controlled adaptor(s) is prevented for a time interval that maybe defined by a user.

The method of flowchart 700 begins with module 702 with one or morecontrollers of a communication network receiving input representative ofmotion being sensed.

The method of flowchart 700 continues with module 704 with eachcontroller, in response to receiving the input, determining whether thedelay mode has been enabled.

The method of flowchart 700 continues with module 706 with eachcontroller, in response to determining the delay mode has not beenenabled, generating a control signal specifying an operation for thecontrolled adaptor(s) of each controller to perform.

The method of flowchart 700 continues with module 708 with eachcontroller, in response to determining the delay mode has not beenenabled, transmitting the generated control signal.

The method of flowchart 700 continues with module 710 with eachcontroller, in response to determining the delay mode has not beenenabled, enabling the delay mode of the source network component. Insome embodiments, the enabling of the delay mode could disable, for thedefined time interval, the ability of the controller configured as amotion sensor to sense motion. In some embodiments, the enabling of thedelay mode could disable the ability of the controller to transmitsubsequent signals to its controlled adaptor(s) for the defined timeinterval. Then, the method of flowchart 700 ends.

Referring now to FIG. 8, flowchart 800 is depicted disclosing an exampleof a fifth method employing message IDs for reducing the number oftransmissions performed by the network components of the communicationnetworks discussed herein, where each network component may include aprocessing unit programmed or configured with execution instructions toperform the method of the flowchart 800. For each network component, theinstructions may be stored in memory communicating with the processingunit and include network ID and device ID parameters of the networkcomponent. In some embodiments, the memory could be configured withinstructions to maintain message ID list of messages received by thenetwork component for a user-defined time interval.

The method of flowchart 800 begins with module 802 with one or morenetwork components of a communication network receiving a control signalhaving a message transmitted from a source network component(s) fromwhich the control signal originates. In some embodiments, the message ofthe control signal could include a message ID parameter representativeof a message ID of the message along with location ID and device IDparameters of a destination network component to which the controlsignal is destined.

The method of flowchart 800 continues with module 804 with each networkcomponent, in response to receiving the control signal, determiningwhether the control signal is eligible for retransmission from at leastthe message ID parameter. In some embodiments, the control signal may bedetermined to be eligible for retransmission if the message ID parameterof the message does not appear on the list of message ID parameters whenthe control signal is received.

The method of flowchart 800 continues with module 806 with each networkcomponent, if the control signal is eligible for retransmission, addingthe message ID parameter to a list of message ID parameters maintained.

The method of flowchart 800 continues with module 808 with each networkcomponent, if the control signal with the message is eligible forretransmission, transmitting the control signal other networkcomponent(s). Then, the method of flowchart 800 ends.

It should be noted that the steps of the method described above may beembodied in computer-readable media stored in a non-transitorycomputer-readable medium as computer instruction code. The method mayinclude one or more of the steps described herein, which one or moresteps may be carried out in any desired order including being carriedout simultaneously with one another. For example, two or more of thesteps disclosed herein may be combined in a single step and/or one ormore of the steps may be carried out as two or more sub-steps. Further,steps not expressly disclosed or inherently present herein may beinterspersed with or added to the steps described herein, or may besubstituted for one or more of the steps described herein as will beappreciated by a person of ordinary skill in the art having the benefitof the instant disclosure.

As used herein, the term “embodiment” means an embodiment that serves toillustrate by way of example but not limitation.

It will be appreciated to those skilled in the art that the precedingexamples and embodiments are exemplary and not limiting to the broadscope of the inventive concepts disclosed herein. It is intended thatall modifications, permutations, enhancements, equivalents, andimprovements thereto that are apparent to those skilled in the art upona reading of the specification and a study of the drawings are includedwithin the broad scope of the inventive concepts disclosed herein. It istherefore intended that the following appended claims include all suchmodifications, permutations, enhancements, equivalents, and improvementsfalling within the broad scope of the inventive concepts disclosedherein.

1-20. (canceled)
 21. A network system, comprising: a plurality ofnetwork components including a source network component and a pluralityof intermediate network components comprising a group of networkcomponents, each network component of the group of network componentscomprising: a transceiver configured to receive and transmit, via ashort-range wireless communications protocol, a control signalcomprising an network ID and group ID parameters and a request for aresponse from a group of network components; a memory storing a networkID, a group ID, and a responder parameter indicating whether or not thenetwork component is configured as a group responder; and a processingunit configured to execute instructions stored in the memory, wherein atleast one intermediate network component is configured to: receive, viathe short-range wireless communications protocol, the control signaloriginating from the source network component and comprised of networkID and group ID parameters and the request for a response from a groupof network components; determine whether the network ID and group ID ofthe intermediate network component matches the network ID and group IDparameters, respectively; and transmit, via the short-range wirelesscommunications protocol, the control signal to at least one othernetwork component of the plurality of network components if there is nota match.
 22. The network system of claim 21, wherein the at least oneintermediate network component is further configured to: determine, ifthere is a match, whether the intermediate network component is a groupresponder based upon its responder parameter; and transmit to the sourcenetwork component, if the intermediate network component is determinedto be a group responder, a response to the request of the controlsignal.
 23. The network system of claim 22, wherein the response to therequest of the control signal includes an expiration parameter.
 24. Thenetwork system of claim 23, wherein the expiration parameter is set tolimit the transmitted response to the request of the control signal islimited one transmission.
 25. The network system of claim 22, wherein achange to a topology of the network system is determined when a groupresponder does not transmit a response to the request of the controlsignal.
 26. The network system of claim 25, wherein a network mappingfunction is initiated when a change to a topology of the network systemis determined.
 27. The network system of claim 21, wherein the group IDparameter is set upon an initiation of a network mapping function.
 28. Amethod for performing transmissions in a network system, comprising:receiving, via a short-range wireless communications protocol and byeach one intermediate network component of a plurality of intermediatenetwork components of a network comprised of a plurality of networkcomponents, a control signal originating from a source network componentof the network and comprised of network ID and group ID parameters and arequest for a response from a group of network components in theplurality of intermediate networks; determining if its network ID andgroup ID matches the network ID and group ID parameters, respectively;and transmitting, via the short-range wireless communications protocol,the control signal to at least one other network component of theplurality of network components if there is not a match.
 29. The methodof claim 28, further comprising: determining, if there is a match,whether the intermediate network component is a group responder basedupon its responder parameter; and transmitting to the source networkcomponent, if the intermediate network component is determined to be agroup responder, a response to the request of the control signal. 30.The method of claim 29, wherein the response to the request of thecontrol signal includes an expiration parameter.
 31. The method of claim30, wherein the expiration parameter is set to limit the transmittedresponse to the request of the control signal is limited onetransmission.
 32. The method of claim 29, wherein a change to a topologyof the network system is determined when a group responder does nottransmit a response to the request of the control signal.
 33. The methodof claim 32, wherein a network mapping function is initiated when achange to a topology of the network system is determined.
 34. The methodof claim 28, wherein the group ID parameter is set upon an initiation ofa network mapping function.
 35. A component of a network, comprising: anetwork component with a processing unit configured to executeinstructions stored in the memory and configured to: receive, via ashort-range wireless communications protocol, a control signal comprisedof network ID and group ID parameters and a request for a response froma group of network components; determine whether the network ID andgroup ID of the network component matches the network ID and group IDparameters, respectively; and transmit, via the short-range wirelesscommunications protocol, the control signal if there is not a match. 36.The component of claim 35, wherein the network component is furtherconfigured to: determine, if there is a match, whether the networkcomponent is a group responder based upon its responder parameter; andtransmit, if the network component is determined to be a groupresponder, a response to the request of the control signal.
 37. Thecomponent of claim 36, wherein the response to the request of thecontrol signal includes an expiration parameter.
 38. The component ofclaim 37, wherein the expiration parameter is set to limit thetransmitted response to the request of the control signal is limited onetransmission.
 39. The component of claim 36, wherein a change to atopology of a network system in which the component belongs isdetermined when the group responder does not transmit a response to therequest of the control signal.
 40. The component of claim 35, whereinthe group ID parameter is set upon an initiation of a network mappingfunction of a network system in which the component belongs.